Domain name system (dns) translations for co-located gateway user planes in wireless communication networks

ABSTRACT

To serve User Equipment (UEs) in a wireless communication network, a control-plane transfers a co-located User Plane Function (UPF) request for a wireless access point ID to a naming system. The naming system detects a co-location translation fault for the wireless access point ID and transfers the wireless access point ID to a controller. The controller determines co-located UPFs for the wireless access node. The controller transfers co-location translation information for the wireless access point ID and co-located UPF IDs to the naming system. The control-plane transfers another co-located UPF request for the wireless access point ID to the naming system. The naming system translates the wireless access point ID into the set of co-located UPF IDs. The naming system transfers the co-located UPF IDs to the control-plane. The control-plane signals the co-located UPFs to serve the UE over the wireless access point.

RELATED CASES

This United States patent application is a continuation of U.S. patentapplication Ser. No. 16/682,344 that was filed on Nov. 13, 2019 and isentitled “DOMAIN NAME SYSTEM (DNS) TRANSLATIONS FOR CO-LOCATED GATEWAYUSER PLANES IN WIRELESS COMMUNICATION NETWORKS.” U.S. patent applicationSer. No. 16/682,344 is hereby incorporated by reference into this UnitedStates patent application.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services include voicecalling, internet access, media streaming, machine communications,vehicle control, and social networking. Exemplary wireless user devicescomprise phones, computers, vehicles, robots, sensors, and drones. Thewireless communication networks have wireless access nodes that exchangewireless signals with the wireless user devices using wireless networkprotocols. Exemplary wireless network protocols include Long TermEvolution (LTE), Fifth Generation New Radio (5GNR), and NarrowbandInternet of Things (NB IoT). LTE, 5GNR, and NB IoT are described inThird Generation Partnership Project (3GPP) documents.

To obtain the wireless data services, the wireless user devices exchangeuser data with the wireless access nodes. The wireless access nodesexchange the user data with Access Gateways (A-GWs) which serve thewireless access points. The A-GWs exchange the user data with ExternalGateways (E-GWs) which anchor external user data communications. TheE-GWs exchange the user data with the external systems. Exemplary A-GWscomprise LTE Serving Gateways (S-GWs) and Fifth Generation Core (5GC)Access User Plane Functions (A-UPFs). Exemplary E-GWs comprise 5GCPacket Data Network Gateways (P-GWs) and 5GC External (E-UPFs).

The A-GWs and the E-GWs are separated into a control plane and a userplane. The control plane handles network signaling and directs the userplane in response to requests from the wireless user devices. The userplane handles user data in response to control instructions from thecontrol plane. When a wireless user device requests a wireless dataservice, the control plane selects a user plane to serve the wirelessuser device. In response a wireless service request, an A-GW ControlPlane (AGW-C) selects an A-GW User Plane (AGW-U), and an E-GW ControlPlane (EGW-C) selects an E-GW User Plane (EGW-U).

To select an AGW-U and an EGW-U to serve the wireless user device, theAGW-U and the EGW-U transfer Domain Name System (DNS) messages thatrequests a translation of a Tracking Area Indicator (TAI) intoIdentifier (IDs) for an AGW-U and EGW-U. The TAI specifies a geographicarea that currently contains the wireless user device. The DNStranslates the TAI for the wireless user device into the AGW-U ID andEGW-U ID. The DNS returns the AGW-U ID and the EGW-U ID to the AGW-C andEGW-C. The AGW-C and EGW-C use the IDs to direct the AGW-U and EGW-U toserve the wireless user device. In response, the AGW-U and EGW-Uexchange user data for the wireless user device.

In some examples, the DNS uses a Dynamic Data Discovery System (DDDS) totranslate the TAI into the AGW-U ID and the EGW-U ID. When using DDDS,the DNS request includes network codes that correlate to services likeLocal Break-Out (LBO), 5GNR Low-Latency (NR), 5GNR/LTE Dual Connectivity(EN), and System Architecture Evolution Dedicated Core (DC). Thus, theDNS selects the AGW-Us and EGW-Us based on the geographic area and thewireless data service for the wireless user device. DNS and DDDS aredescribed by various Internet Engineering Task Force (IETF) documents.

Unfortunately, some DNS translations may be missing from the DNS.Moreover, the replacement DNS translations do not efficiently identifyco-located AGW-Us and EGW-Us or edge AGW-Us and EGW-Us.

TECHNICAL BACKGROUND

To serve User Equipment (UEs) in a wireless communication network, acontrol-plane transfers a co-located User Plane Function (UPF) requestfor a wireless access point ID to a naming system. The naming systemdetects a co-location translation fault for the wireless access point IDand transfers the wireless access point ID to a controller. Thecontroller determines co-located UPFs for the wireless access node. Thecontroller transfers co-location translation information for thewireless access point ID and co-located UPF IDs to the naming system.The control-plane transfers another co-located UPF request for thewireless access point ID to the naming system. The naming systemtranslates the wireless access point ID into the set of co-located UPFIDs. The naming system transfers the co-located UPF IDs to thecontrol-plane. The control-plane signals the co-located UPFs to servethe UE over the wireless access point.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network to serve UserEquipment (UEs) with data communication services over co-located edgeGateway User Planes (GW-Us).

FIG. 2 illustrates the operation of the wireless communication networkto serve the UEs with the data communication services over theco-located edge GW-Us.

FIG. 3 illustrates the operation of the wireless communication networkto serve the UEs with the data communication services over theco-located edge GW-Us.

FIG. 4 illustrates the operation of the wireless communication networkto generate Domain Name System (DNS) translations for the co-locatededge GW-Us.

FIG. 5 illustrates the operation of the wireless communication networkto serve the UEs with the data communication services over theco-located edge GW-Us.

FIG. 6 illustrates a Network Function Virtualization Infrastructure(NFVI) to serve a UE with data communication services over co-locatedGW-Us.

FIG. 7 illustrates the UE that receives the data communication servicesover the co-located GW-Us.

FIG. 8 illustrates an Access Point (AP) that serves the UE with the datacommunication services over co-located GW-Us.

FIG. 9 illustrates the operation of the UE, AP, and NFVI to serve the UEwith the data communication services over co-located edge GW-Us.

FIG. 10 illustrates a Fifth Generation New Radio (5GNR) communicationnetwork to serve a UE with data communication services over co-locatededge User Plane Functions (UPFs).

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 serve UserEquipment (UEs) 101-103 with data communication services over co-locatedAccess Gateway User Plane (AGW-U) 123 and External Gateway User Plane(EGW-U) 133. Wireless communication network 100 comprises User Equipment(UEs) 101-103, Access Points (APs) 111-113, AGW-Us 121-123, EGW-Us131-133, GW Control Plane (GW-C) 140, Domain Name System (DNS) 150, andtranslation controller 160. Wireless communication network 100 isrestricted for clarity and typically includes more UEs, APs, and GWsthan the amount shown.

AGW-U 123 and EGW-U 133 are co-located at network edge “A”. For example,AGW-U 123 and EGW-U 133 may reside in the same computer, and thecomputer may be physically adjacent to the computer that hosts part ofAP 113. In this context, GW co-location requires the distance betweenthe serving AGW-U and the serving EGW-U to be less than 1000 feet,although the distance is typically much smaller and is oftenvirtualized. In this context, a network edge location requires thedistance between the serving AGW-U and the serving AP to be less than1000 feet, although the distance is typically much smaller and is oftenvirtualized. In a co-located edge location, the AP, AGW-U, and EGW-U areall geographically proximate to one another. In wireless communicationnetwork 100, GW-Us 121 and 131 are co-located in an integrated SystemArchitecture Evolution (SAE) GW in a network core. GW-Us 122 and 132 arenot co-located. GW-Us 123 and 133 are co-located at the network edge,and thus, AP 113, AGW-U 123, and EGW-U 133 are all close together.

UEs 101-103 are capable of wirelessly linking to APs 111-113 and someUEs handover from one AP to another as they move around. On FIG. 1, UE101 is shown linked to AP 111 and UEs 102-103 are linked to AP 113. Thewireless links may use Institute of Electrical and Electronic Engineer(IEEE) 802.11 (WIFI), Long Term Evolution (LTE), Fifth Generation NewRadio (5GNR), Narrowband Internet-of-Things (NB-IoT), or some otherwireless protocol. LTE, 5GNR, and NB-IoT are described by ThirdGeneration Partnership Project (3GPP) documents. WIFI, LTE, 5GNR, andNB-IoT may use frequencies in the low-band, mid-band, millimeter-waveband, and/or some other part of the wireless spectrum.

APs 111-113 are linked to AGW-Us 121-123 and GW-C 140 over backhaullinks. These backhaul links may use IEEE 802.3 (Ethernet), Time DivisionMultiplex (TDM), Data Over Cable System Interface Specification(DOCSIS), Internet Protocol (IP) LTE, 5GNR, WIFI, or some other dataprotocol. These backhaul may be virtualized for co-located APs andAGW-Us. AGW-Us 121-123 are linked to EGW-Us 131-133 over network links.These network links may use Ethernet, TDM, DOCSIS, IP, LTE, 5GNR, WIFI,or some other data protocol. In some examples, the network links arevirtualized for co-located AGW-Us and EGW-Us. EGW-Us 131-133 are linkedto external data systems like the internet and enterprise networks. GW-C140, DNS 150, and translation controller 160 are linked together. GW-C140 is linked to AGW-Us 121-123 and EGW-Us 131-133. Translationcontroller 160 monitors APs 111-113, AGW-Us 121-123 and EGW-Us 131-133to detect network topology.

UEs 101-103 comprise user circuitry that interacts with users. UEs101-103 also comprise radio circuitry that wirelessly communicates withAPs 111-113. UEs 101-103 might be phones, computers, robots, sensors,vehicles, drones, data appliances, or some other user apparatus withwireless communication circuitry.

APs 111-113 serve UEs 101-103 with wireless communication services. APs111-113 comprise antennas, modulators, amplifiers, filters,digital/analog interfaces, microprocessors, memory, software,transceivers, and bus connections. The microprocessors comprise DigitalSignal Processors (DSPs), Central Processing Units (CPUs), GraphicalProcessing Units (GPUs), Field Programmable Gate Arrays (FPGAs),Application-Specific Integrated Circuits (ASICs), and/or the like. Thememory comprises Random Access Memory (RAM), flash circuitry, diskdrives, and/or the like. The memory stores software like operatingsystems, network applications, and virtual components. Exemplary networkapplications comprise Physical Layer (PHY), Media Access Control (MAC),Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), RadioResource Control (RRC), and Service Data Adaptation Protocol (SDAP),although other network applications could be used.

In APs 111-113, the microprocessors execute the operating systems andnetwork applications to wirelessly exchange network signaling and userdata with UEs 101-103 over the wireless links. The microprocessorsexecute the operating systems and network applications to exchangenetwork signaling with GW-C 140 and to exchange user data with AGW-Us121-123 over the backhaul links. APs 111-113 may comprise LTE eNodeBs,NR gNodeBs, WIFI hotspots, NB IoT nodes, and/or some other wireless basestations that serve both UEs and AGW-Us.

AGW-Us 121-123 serve APs 111-113 with core access over the backhaullinks. EGW-Us 131-133 communicate with external systems like theinternet and enterprise networks. AGW-Us 121-123 and EGW-Us 131-133comprise microprocessors, memory, software, transceivers, and busconnections. The microprocessors comprise CPUs, GPUs, ASICs, and/or thelike. The memory comprises RAM, flash circuitry, disk drives, and/or thelike. The memory stores software like operating systems, virtualcomponents, and network functions. AGW-Us 121-123 may comprise UserPlane Functions (UPFs), Serving Gateway User Planes (SGW-Us), and/orsome other user data handler that serves APs and interacts with EGW-Us.EGW-Us 131-133 may comprise UPFs, Packet Data Network Gateway UserPlanes (PGW-Us), and/or some other user data handler that servesexternal systems and interacts with AGW-Us.

AGW-U 121 and EGW-U 131 comprise an integrated SAE GW in a Dedicated SAECore (DC). DC delivers a specific set of network services based on theindividual UE subscription. For example, robot UEs may use aMachine-to-Machine (M2M) DC, vehicle UEs may use a Vehicle-to-X (V2X)DC, and corporate employees may use an enterprise DC. AGW-U 123 supportsLocal Break-Out (LBO) and low-latency New Radio (NR) with its edgelocation and co-location with EGW-U 133. EGW-U 133 supports LBO and NRwith its edge location and its co-location with AGW-U 123. LBO comprisesedge internet-access without traversing the wireless network core. NRcomprises Ultra Low Latency (ULL) 5GNR service with very strict timingrequirements. Co-located edge AGW-Us and EGW-Us deliver superior LBO andlow-latency NR. In some examples, the proximity of AP 113, AGW-U 123,and AGW-U 133 allows the virtualization of the fronthaul, backhaul, andnetwork links. For example, the AP 113 baseband, AGW-U 123, and EGW-U133 may be hosted in the same computer center to serve exceptional LBO,5GNR, and BB IoT services.

GW-C 140, DNS 150, and translation controller 160 each comprisemicroprocessors, memory, software, transceivers, and bus connections.The microprocessors comprise CPUs, GPUs, ASICs, and/or the like. Thememory comprises RAM, flash circuitry, disk drives, and/or the like. Thememory stores software like operating systems, virtual components, andnetwork functions. GW-C 140 comprises network functions like SAE GWControl Planes (SAE GW-Cs), SGW control planes (SGW-Cs), PGW controlplanes (PGW-Cs), Access and Mobility Management Functions (AMFs),Session Management Functions (SMFs), Mobility Management Entities(MMEs), and/or some other network controllers that serve UEs over APs.DNS 150 comprises network functions like address databases, resolvers,Dynamic Delegation Discovery System (DDDS) modules, and/or some othernetwork controllers that serve GW-Cs with GW-U IDs. Translationcontroller 160 comprises network functions like network topologydatabases, Border Gateway Protocol (BGP) listeners, edge co-locationmodules, translation engines, and/or some other network controllers thatserve DNS with DNS translations for co-located AGW-Us and E-GW-Us.

In operation, UE 101 wirelessly attaches to AP 111, and AP 111responsively transfers a session request to GW-C 140. GW-C 140 receivesthe session request from AP 111 for UE 101 and responsively transfers anAGW-U request for UE 101 that has network data and an AP Identifier (ID)for AP 111. The network data indicates Tracking Area Identifier (TAI),network service data, UE information, and/or other communication data.The network service data may indicate Local Break-Out (LBO), low-latencyNew Radio (NR), LTE/NR Dual Connectivity (EN), Access Point Name (APN),and/or some other network characteristics. The UE information mayindicate a type of SAE Dedicated Core (DC), NR, EN, and/or some other UEcharacteristics.

DNS 150 receives the AGW-U request and translates the AP ID and somenetwork data into an AGW-U ID for AGW-U 121. AGW-U 121 and EGW 131 forman integrated SAE GW in a dedicated SAE core. DNS 150 may translate theAP ID into a data set identifying AGW-Us 121-123 and then select AGW-U121 based on the “DC” in the network data. DNS 150 transfers an AGW-Uresponse that has the AGW-U ID for AGW-U 121. GW-C 140 receives theAGW-U response and transfers an EGW-U request that has the network datathe AGW-U ID for AGW-U 121.

DNS 150 receives the EGW-U request and translates the AGW-U ID for AGW-U121 and some network data into an EGW-U ID for EGW-U 131. EGW-U 131 ispart of the integrated SAE GW in the dedicated SAE core. DNS 150 maytranslate the AGW-U ID into a data set identifying EGW-Us 131-133 andthen select EGW-U 131 based on the “DC” in the network data. DNS 150transfers an EGW-U response that has the EGW-U ID for EGW-U 131. GW-C140 receives the EGW-U response and responsively transfers AGW-U controlsignals using the AGW-U ID and also transfers EGW-U control signalsusing the EGW-U ID. AP 111 serves UE 101. AGW-U 121 serves UE 101 overAP 111 responsive to the AGW-U control signals. EGW-U 131 serves UE 101responsive to the EGW-U control signals. Thus, user data flows betweenUE 101 and external systems over AP 111 and the integrated SAE GW thatcomprises AGW-U 121 and EGW-U 131.

UE 103 wirelessly attaches to AP 113, and AP 113 responsively transfersa session request to GW-C 140. GW-C 140 receives the session requestfrom AP 113 for UE 103 and responsively transfers an AGW-U request forUE 103 that has network data and an AP ID for AP 113. The network dataindicates TAI, network service data, UE information, and/or some othercommunication data. The network service data may indicate LBO, NR, EN,and/or some other network application. The UE information may indicateDC, NR, EN, and/or some other UE characteristics.

DNS 150 receives the AGW-U request and translates the AP ID and somenetwork data into an AGW-U ID for AGW-U 123. AGW-U 123 supports LBO andis co-located with EGW-U 133 near AP 113. DNS 150 may translate the APID into a data set identifying AGW-Us 121-123 and then select AGW-U 123based on “LBO” in the network data. DNS 150 transfers an AGW-U responsethat has the AGW-U ID for AGW-U 123. GW-C 140 receives the AGW-Uresponse and transfers an EGW-U request that has the network data theAGW-U ID for AGW-U 123.

DNS 150 receives the EGW-U request and translates the AGW-U ID for AGW-U123 and some network data into an EGW-U ID for EGW-U 133. EGW-U 133supports LBO and is co-located with AGW-U 123 at the network edge nearAP 113. DNS 150 may translate the AP ID into a data set identifyingEGW-Us 131-133 and then select EGW-U 133 based on the LBO andco-location. To detect co-location, DNS 150 detects the same location ID(like “EDGE A”) in both the AGW-U ID and in the EGW-U ID. DNS 150transfers an EGW-U response that has the EGW-U ID for EGW-U 133. GW-C140 receives the EGW-U response and responsively transfers AGW-U controlsignals using the AGW-U ID and transfers EGW-U control signals using theEGW-U ID. AP 113 serves UE 103. AGW-U 131 serves UE 103 over AP 113responsive to the AGW-U control signals. EGW-U 133 serves UE 103responsive to the EGW-U control signals. Thus, user data flows betweenUE 103 and external systems over AP 113, AGW-U 123, and EGW-U 133.Moreover, AP 113, AGW-U 123, and EGW-U 133 may be virtualized to serveexceptional LBO or low-latency NR.

UE 102 wirelessly attaches to AP 113, and AP 113 responsively transfersa session request to GW-C 140. GW-C 140 receives the session requestfrom AP 113 for UE 102 and responsively transfers an AGW-U request forUE 102 that has network data and an AP ID for AP 113. The network dataindicates TAI, network service data, UE information, and/or some othercommunication data. The network service data may indicate LBO, NR, EN,and/or some other network application. The UE information may indicateDC, NR, EN, and/or some other UE characteristics.

DNS 150 receives the AGW-U request and translates the AP ID and networkdata into an AGW-U ID for AGW-U 123. AGW-U 123 supports an NRlow-latency service and is co-located with EGW-U 133 at the network edgenear AP 113. DNS 150 may translate the AP ID into a data set identifyingAGW-Us 121-123 and then select AGW-U 123 based on an NR low-latencyservice indicated in the network data. DNS 150 transfers an AGW-Uresponse that has the AGW-U ID for AGW-U 123. GW-C 140 receives theAGW-U response and transfers an EGW-U request that has the network datathe AGW-U ID for AGW-U 123.

DNS 150 receives the EGW-U request and translates the AGW-U ID for AGW-U123 and some network data into an EGW-U ID for EGW-U 133. EGW-U 133supports the NR low-latency service and is co-located with AGW-U 123 atthe network edge near AP 113. DNS 150 may translate the AP ID into adata set identifying EGW-Us 131-133 and then select EGW-U 133 based onthe NR service indicated in network data. DNS 150 transfers an EGW-Uresponse that has the EGW-U ID for EGW-U 133. GW-C 140 receives theEGW-U response and responsively transfers AGW-U control signals usingthe AGW-U ID and also transfers EGW-U control signals using the EGW-UID. AP 113 serves UE 102. AGW-U 131 serves UE 102 over AP 113 responsiveto the AGW-U control signals. EGW-U 133 serves UE 102 responsive to theEGW-U control signals. Thus, user data may flow between UEs 102-103 overAP 113, AGW-U 123, and EGW-U 133. Moreover, AP 113, AGW-U 123, and EGW-U133 may be virtualized together and serve an exceptional NR low-latencyservice like Vehicle-to-Vehicle (V2V) communications.

Now consider an example where some translations are missing from DNS150. In particular, the translations of the AP ID for AP 113 aremissing. Perhaps AP 113 is new. In this example, UE 102 wirelesslyattaches to AP 113, and AP 113 transfers a session request to GW-C 140.GW-C 140 receives the session request from AP 113 for UE 102 andresponsively transfers an AGW-U request for UE 102 that has network dataand an AP ID for AP 113. GW-C 160 receives a session request from AP 113for UE 102 and transfers an AGW-U request that indicates the networkdata for UE 102 and the AP ID for AP 113.

DNS 150 receives the AGW-U request and attempts to translate the AP IDand network data into an AGW-U ID. Since the translations for AP 113 aremissing at this point, DNS 150 detects a translation fault for AP 113and transfers an AGW-U response that indicates a translation fault forthe AP 113 ID. GW-C 140 receives the AGW-U response that indicates thetranslation fault for the AP 113 ID.

In response to the translation fault, GW-C 140 transfers a translationrequest that has the TAI for UE 102. DNS 150 receives the translationrequest and translates the TAI into AGW-U IDs for AGW-Us 121-123 andinto EGW-U IDs for EGW-Us 131-133. DNS 150 transfers a translationresponse that indicates the AGW-U IDs and the EGW-U IDs for the TAI.GW-C 140 selects an AGW-U and an EGW-U to serve UE 102 from the list ofGW-U IDs from DNS 150. Unfortunately, the TAI translations are notoptimized for the network services.

In response to the translation fault, GW-C 140 transfers a translationfault notice that indicates the TAI for UE 102, AP ID for AP 113, andnetwork instructions. In some examples, GW-C 140 caches DNS misses untila DNS miss pattern is established, and then GW-C 140 transfers thetranslation fault notice for AP 113. Translation controller 160 receivesthe translation fault notice and transfers a translation request thathas the TAI for UE 102. DNS 150 receives the translation request andtranslates the TAI into AGW-U IDs for AGW-Us 121-123 and into EGW-U IDsfor EGW-Us 131-133. DNS 150 transfers a translation response thatindicates the AGW-U IDs and the EGW-U IDs for the TAI.

Translation controller 160 receives the translation response andprocesses the AGW-U IDs and the EGW-U IDs against network topology datato determine co-located groups of the AGW-Us and the EGW-Us. Translationcontroller 160 also determines whether the co-location is at the networkedge or in a dedicated SAE core. Translation controller 160 addslocation IDs to the AGW-U IDs and the EGW-U IDs to indicate co-locationby having co-located GW-Us share a location ID like “EDGE A” or “COREB.” Translation controller 160 also indicates edge or core proximity byhaving GW-U IDs use location IDs like “EDGE A” or “CORE B.”

Translation Controller 160 adds network data like LBO, NR, EN, or DC tobranch the translations for AP 113 based on the network data. DC isbranched to integrated SAE core AGW-U 121 and EGW-U 131. LBO and NR arebranched to co-located edge AGW-U 123 and EGW-U 133. TranslationController 160 generates translations of the AP ID for AP 113 into theAGW-U IDs and adds the network data to branch DNS translations toco-located AGW-U IDs and EGW-U IDs as desired. Translation controller160 transfers the DNS translations to DNS 150. Now when a UE wirelesslyattaches to AP 113 for a network service, DNS 150 will translate theAGW-U request that has the AP ID for AP 113 and network data into theAGW-U IDs and the EGW-U IDs that are optimally configured deliver thespecific network service as described herein.

Advantageously, translation controller 160 responds to missing DNStranslations by effectively generating new DNS translations forco-located and edge AGW-Us 121-123 and EGW-Us 131-133.

FIG. 2 illustrates the operation of wireless communication network 100to serve a UE with LBO service over co-located edge GW-Us. A UEwirelessly attaches to an AP (201). The AP transfers a session requestfor the UE to the GW-C (201). The GW-C transfers an AGW-U request to aDNS that has LBO data and an AP ID (201). The DNS attempts to translatethe AP ID and LBO data into an AGW-U ID (202). If the AP ID translationis present (203), the DNS translates the AP ID and LBO data into anAGW-U ID for an AGW-U that supports LBO at the network edge (204). TheDNS transfers an AGW-U response that has the AGW-U ID (204).

The GW-C receives the AGW-U response and transfers an EGW-U request thathas the LBO data and the AGW-U ID (205). The DNS receives the EGW-Urequest and translates the AGW-U ID and LBO data into an EGW-U ID for anEGW-U that supports LBO and is co-located with the selected AGW-U (206).To detect edge co-location, the DNS detects the same edge location ID(like “EDGE A”) in the AGW-U ID and in the EGW-U ID (206). The DNStransfers an EGW-U response that has the EGW-U ID for the EGW-U (206).The GW-C receives the EGW-U response and responsively transfers AGW-Ucontrol signals using the AGW-U ID and transfers EGW-U control signalsusing the EGW-U ID (207). The AGW-U and EGW-U serve the UE responsive tothe control signals to serve optimized LBO to the UE (207). Theoperation repeats (201).

If the AP translation is missing from the DNS (203), the DNS transfersan AGW-U response to the GW-C that indicates a translation fault for theAP ID and network instructions (208). The GW-C transfers a translationfault notice that indicates the TAI for the UE and the LBO data (209).The translation controller receives the translation fault notice andtransfers a translation request that has the TAI for the UE to the DNS(210). The DNS translates the TAI into AGW-U IDs and into EGW-U IDs(211). The DNS transfers a translation response that indicates the AGW-UIDs and the EGW-U IDs for the TAI (211).

The translation controller processes the AGW-U IDs and the EGW-U IDsagainst network topology data to determine co-located groups of theAGW-Us and the EGW-Us at the network edge (212). The translationcontroller adds location IDs to the AGW-U IDs and the EGW-U IDs toindicate edge co-location by having co-located GW-Us share a location IDlike “EDGE 113” (212). The translation controller adds LBO data to thetranslation input to branch the translations for AP 113 and LBO toco-located edge AGW-Us and EGW-Us (212). The generation of translationsfor network services like NR, EN, and DC would be similar. Thetranslation controller transfers the translations to the DNS (212) andthe operation repeats (201).

Although not shown for clarity, the GW-C transfers a translation requestwith the TAI to the DNS in response to the translation fault. The DNStranslates the TAI into AGW-U IDs and into EGW-U IDs and transfers atranslation response that indicates the AGW-U IDs and the EGW-U IDs forthe TAI. The GW-C selects an AGW-U ID and an EGW-U ID for the UE fromthe translation response. The GW-C transfers AGW-U control signals usingthe AGW-U ID and transfers EGW-U control signals using the EGW-U ID. TheAGW-U and EGW-U serve the UE responsive to the control signals.Unfortunately, the TAI translations for the AP are not optimized for thenetwork services.

FIG. 3 illustrates the operation of wireless communication network 100to serve UE 101 with data communication services over co-located edgeGW-Us 123 and 133. UE 101 wirelessly attaches to AP 111, and AP 111responsively transfers a session request (RQ) to GW-C 140. GW-C 140responsively transfers an AGW-U request that has the AP ID for AP 111and network data that indicates the TAI for UE 102 and a special networkservice. The special network service (like LBO or low-latency NR) isoptimized by using co-located edge GW-Us.

DNS 150 receives the AGW-U request and translates the AP ID for AP 111and a special network service ID into an AGW-U ID for AGW-U 123. AGW-U123 supports the special network service and is located near AP 111. Forexample, DNS 150 may translate the AP ID into a set of AGW-Us 121-123and then select AGW-U 123 based on an LBO indicator in the network data.DNS 150 transfers an AGW-U response that has the AGW-U ID for AGW-U 123.GW-C 140 receives the AGW-U response and transfers an EGW-U request thathas the network data the AGW-U ID for AGW-U 123.

DNS 150 receives the EGW-U request and translates the AGW-U ID for AGW-U123 and the special network service ID into an EGW-U ID for EGW-U 133.EGW-U 133 supports the special network service and is co-located withAGW-U 123 at the network edge. DNS 150 may translate the AGW-U ID into aset of EGW-Us 131-133 and then select co-located EGW-U 133 based on anLBO indication in the network data. To determine co-location, DNS 150detects the same location ID (like “EDGE 111”) in both the AGW-U ID andin the EGW-U ID. DNS 150 transfers an EGW-U response that has the EGW-UID for co-located EGW-U 133. GW-C 140 receives the EGW-U response andresponsively transfers AGW-U control signals using the AGW-U ID andtransfers EGW-U control signals using the EGW-U ID. AP 111 serves UE101. AGW-U 123 serves UE 101 responsive to the AGW-U control signals.EGW-U 133 serves UE 101 responsive to the EGW-U control signals. Thus,user session data flows between UE 101 and external systems over AP 111,AGW-U 123, and EGW-U 133. Moreover, AP 111, AGW-U 123, and EGW-U 133 maybe virtualized together to serve exceptional LBO.

FIGS. 4-5 illustrate the operation of wireless communication network 100to generate DNS translations for AP 112 and co-located edge GW-Us 123and 133 to serve UE 103 with the special network service. The specialnetwork service is optimized by using co-located edge GW-Us 123 and 133,but the translations for AP 112 are missing from DNS 150.

Referring to FIG. 4, UE 102 wirelessly attaches to AP 112, and AP 112transfers a session request to GW-C 140. GW-C 140 receives the sessionrequest from AP 112 and responsively transfers an AGW-U request thatindicates the special network service and the AP ID for AP 112. DNS 150receives the AGW-U request and attempts to translate the AP ID for AP112 into an AGW-U ID. Since these translations are currently missing,DNS 150 detects a translation fault and transfers an AGW-U response thatindicates the translation fault for AP 112. GW-C 140 receives the AGW-Uresponse that indicates the translation fault for AP 112.

In response to the translation fault, GW-C 140 transfers a translationfault notice that indicates the TAI for UE 102, the AP ID for AP 112,and network service instructions. Translation controller 160 receivesthe translation fault notice and transfers a translation request to DNS150 that has the TAI for UE 102. DNS 150 receives the translationrequest and translates the TAI into AGW-U IDs for AGW-Us 121-123 andinto EGW-U IDs for EGW-Us 131-133. DNS 150 transfers a translationresponse that indicates the AGW-U IDs and the EGW-U IDs for the TAI ofUE 102.

Translation controller 160 receives the translation response andprocesses the AGW-U IDs and the EGW-U IDs against network topology datato determine co-located groups of the AGW-Us and the EGW-Us. Translationcontroller 160 also determines whether the co-location is at the networkedge. To determine edge location and co-location, translation controller160 monitors wireless communication network 100 to discovercommunication links between APs, AGW-Us, and EGW-Us. Translationcontroller 160 then enters a network topology database to identifygeographic information for the linked APs, AGW-Us, and EGW-Us. Thegeographic information could be geographic coordinates, data center IDs,computer system IDs, and/or the like. Translation controller 160processes the geographic information for the APs, AGW-Us, and EGW-Us todetect co-located AGW-Us and EGW-Us and to detect their proximity theAPs.

Translation controller 160 adds location IDs to the AGW-U IDs and to theEGW-U IDs to indicate edge co-location by having co-located edge GW-Usshare an edge location ID like “EDGE 112.” Translation controller 160also adds the special network service data (like LBO or NR) to branchthe translations for AP 112 and the special network service to AGW-U 123and EGW-U 133 which are co-located at EDGE 112. Translation controller160 transfers the translations for AP 112 to DNS 160. DNS 160 may nowuse the translations to serve UEs like UE 103.

Referring to FIG. 5, UE 103 wirelessly attaches to AP 112, and AP 112responsively transfers a session request to GW-C 140. GW-C 140responsively transfers an AGW-U request that has the AP ID for AP 112and network data that indicates the special network service that isoptimized by using co-located edge GW-Us. DNS 150 receives the AGW-Urequest and translates the AP ID for AP 112 and the special networkservice ID into an AGW-U ID for AGW-U 123. AGW-U 123 supports thespecial network service and is located near AP 112. For example, DNS 150may translate the AP ID into a set of AGW-Us 121-123 and then selectAGW-U 123 based on an LBO indicator in the AGW-U request. DNS 150transfers an AGW-U response that has the AGW-U ID for AGW-U 123. GW-C140 receives the AGW-U response and transfers an EGW-U request that hasthe network data the AGW-U ID for AGW-U 123.

DNS 150 receives the EGW-U request and translates the AGW-U ID for AGW-U123 and the special network service ID into an EGW-U ID for EGW-U 133.EGW-U 133 supports the special network service and is co-located withAGW-U 123 at the network edge. DNS 150 may translate the AGW-U ID into aset of EGW-Us 131-133 and then select co-located EGW-U 133 based on theLBO indication in the network data and the shared location ID (EDGE 112)in both the AGW-U ID and in the EGW-U ID. DNS 150 transfers an EGW-Uresponse that has the EGW-U ID for co-located edge EGW-U 133.

GW-C 140 receives the EGW-U response and responsively transfers AGW-Ucontrol signals using the AGW-U ID and transfers EGW-U control signalsusing the EGW-U ID. AP 112 serves UE 103. AGW-U 123 serves UE 103responsive to the AGW-U control signals. EGW-U 133 serves UE 103responsive to the EGW-U control signals. Thus, user session data flowsbetween UE 103 and external systems over AP 112, AGW-U 123, and EGW-U133. Moreover, AP 112, AGW-U 123, and EGW-U 133 may be virtualizedtogether to optimally serve the special network service.

FIG. 6 illustrates Network Function Virtualization Infrastructure (NFVI)670 to serve UE 601 with data communication services over co-locatedGW-Us. NFVI 670 is an example of AGW-Us 121-123, EGW-Us 131-133, GW-C140, DNS 150, and translation controller 160, although these componentsmay vary from NFVI 670. NFVI 670 may have an edge location, corelocation, and/or some other location. NFVI 670 may use a single locationor be distributed across multiple locations. NFVI 670 comprises NFVIhardware, hardware drivers, operating systems and hypervisors, NFVIvirtual layers, and Virtual Network Functions (VNFs). The NFVI hardwarecomprises Network Interface Cards (NICs), CPUs, RAM, disk storage, anddata switches (SWS). The virtual layers comprise virtual NICs (vNIC),virtual CPUs (vCPU), virtual RAM (vRAM), virtual Disk Storage (vDISK),and virtual Switches (vSW). The VNFs comprise Mobility Management Entity(MME) 640, Serving Gateway Control Plane (SGW-C) 641, Packet DataNetwork Gateway Control Plane (PGW-C) 642, SGW User Planes (SGW-Us), PGWUser Planes (PGW-Us), Application (APP) DNS 650, Operator (OP) DNS 651,DNS manager 660, and Border Gateway Protocol (BGP) listener 661.

MME 640, SGW-C 641, and PGW-C 642 comprise an example of GW-C 140,although GW-C 140 may differ. APP DNS 650 and OP DNS 651 comprise anexample of DNS 150, although DNS 150 may differ. DNS manager 660 and BGPlistener 661 comprise an example of translation controller 160, althoughtranslation controller 160 may differ. In some example an Access andMobility Management Function (AMF) could replace or supplement MME 640.Other VNFs are typically present like Policy Control Function (PCF),Session Management Function (SMF), Authentication and Security Function(AUSF), Unified Data Management (UDM), Network Slice Selection Function(NSSF), Network Repository Function (NRF), Network Exposure Function(NEF), and User Plane Function (UPF). The NFVI hardware executes thehardware drivers, operating systems, hypervisors, virtual layers, andVNFs to serve UE 601 over AP 611.

In operation, UE 601 wirelessly attaches to AP 611, and AP 611 transfersan initial UE message to MME 640. MME 643 interacts with UE 601 andother VNFs to authenticate and authorize UE 601 and to select a servicelike LBO, NR, EN, or DC. MME 640 selects SGW-C 641 and PGW-C 642 basedon the selected service, UE 601 TAI, AP 611 ID, and/or some otherfactors. MME 640 transfers a create session request for UE 601 to SGW-C641. The create session request has the AP 611 ID and network data likeLBO, NR, EN, or DC. In response to the create session request, SGW-C 641transfers an SGW-U request to APP DNS 650. The SGW-U request has the AP611 ID and the network data.

APP DNS 650 receives the SGW-U request having the AP 611 ID and thenetwork data. APP DNS 650 and SGW-C 641 perform a Dynamic DelegationDiscovery System (DDDS) session to translate the AP ID and the networkdata into the SGW-U ID. In response to the network data like LBO, APPDNS 650 may select an SGW-U ID that has an edge location ID for AP 611.In response to the network data like DC, APP DNS 650 may select an SGW-UID that has an SAE core ID.

APP DNS 650 transfers an SGW-U response that has the SGW-U ID for theselected SGW-U. SGW-C 641 receives the SGW-U response and uses the SGW-UID to transfer SGW-U control signaling to the selected SGW-U to supportthe session. SGW-C 641 also transfers a create session request for UE601 to PGW-C 642. The create session request has the SGW-U ID, AP 611ID, and network data like LBO, NR, EN, or DC. PGW-C 642 receives thecreate session request and transfers a PGW-U request to APP DNS 650. ThePGW-U request has the SGW-U ID and the network data.

APP DNS 650 receives the PGW-U request having the SGW-U ID and thenetwork data. APP DNS 650 and PGW-C 642 perform a DDDS session totranslate the SGW-ID and the network data into the PGW-U ID. In responseto the network data that indicates a preference for co-location, APP DNS650 may select a PGW-U ID that shares a location ID with the SGW-U ID.In response to the network data, APP DNS 650 may select a PGW-U ID thatshares the SAE core ID with the SGW-U ID. APP DNS 650 transfers a PGW-Uresponse that has the PGW-U ID. PGW-C 642 receives the PGW-U responseand uses the PGW-U ID to transfer PGW-U control signaling to theselected PGW-U to support the session.

AP 611 wirelessly serves UE 601. The selected SGW-U and PGW-U serve UE601 over AP 611 responsive to the control signals. Thus, user data flowsbetween UE 601 and the external systems over AP 611 and the selectedSGW-U and PGW-U. In examples where NFVI 670 is located at the edge nextto AP 611, the selected SGW-U and PGW-U serve excellent LBO and NRservices to UE 601. In examples where NFVI 670 is located in the core,the selected SGW-U and PGW-U serve excellent DC services to UE 601.

To generate the DNS translations for AP 611, UE 601 (or another UE)wirelessly attaches to AP 611, and AP 611 transfers a session request toMME 640. MME 640 authenticates, authorizes, selects a service for UE611. MME 640 transfers a create session request to SGW-C 641. SGW-C 641receives the session request from AP 611 and transfers an SGW-U requestthat indicates the AP 611 ID and the network data. DNS 150 receives theSGW-U request and attempts to translate the AP ID for AP 611 into anSGW-U ID. Since the translations for AP 611 are missing, APP DNS 650detects a translation fault and transfers an SGW-U response thatindicates the translation fault for AP 611.

SGW-C 641 receives the SGW-U response that indicates the translationfault for AP 611. In response, SGW-C 641 and PGW-C 642 transfer GW-Urequests to OP DNS 651 to translate the TAI for UE 601 into an SGW-U IDand a PGW-U ID. OP DNS 651 translates the TAI for UE 601 into an SGW-UID and a PGW-U ID and returns the IDs to SGW-C 641 and PGW-C 642. SGW-C641 and PGW-C 642 use the selected GW-U IDs to select and control anSGW-U and PGW-U which serve UE 601 over AP 611. Unfortunately, the TAItranslations are not optimized for the network service.

Also in response to the translation fault, SGW-C 640 transfers atranslation fault notice that indicates the TAI for UE 601, the AP IDfor AP 611, and processing instructions for network codes like LBO, NR,EN, and DC. In some examples, SGW-C 640 caches DNS misses until a DNSmiss pattern is established for AP 611, and then SGW-C 640 transfers thetranslation fault notice for AP 611. DNS controller (CNT) 660 receivesthe translation fault notice and transfers a translation request to OPDNS 651 that has the TAI for UE 601. OP DNS 651 receives the translationrequest and translates the TAI into SGW-U IDs and PGW-U IDs. OP DNS 651transfers a translation response that indicates the SGW-U IDs and thePGW-U IDs for the TAI of UE 601.

DNS controller 660 receives the translation response and processes theSGW-U IDs and the PGW-U IDs against network topology data to determineco-located groups of the SGW-Us and PGW-Us. DNS controller 660 alsodetermines whether the co-location is at the network edge or in adedicated SAE core. To determine edge and core co-location, BGP listener661 monitors network traffic to discover communication links between AP611, the SGW-Us, and the PGW-Us. DNS controller 660 then enters anetwork topology database to identify geographic information for AP 611and any detected SGW-Us and PGW-Us. The geographic information could begeographic coordinates, location IDs, NFVI IDs, and/or the like. DNScontroller 660 processes the geographic information for AP 611, theSGW-Us, and the PGW-Us to detect co-located SGW-Us and PGW-Us. DNScontroller 660 also processes the geographic information to detect edgeproximity to AP 611.

To indicate edge co-location where detected, DNS controller 660 adds ashared location ID for AP 611 like “EDGE 611” to the co-located SGW-UIDs and PGW-U IDs. Per the service instructions, DNS controller 660 alsoadds network data (like LBO, NR, EN, or DC) to branch the translationsfor AP 611 based on the network data. For example, LBO and NR nodes areadded to translate the AP 611 ID into co-located edge GW-Us when LBO orNR network data is provided. DC nodes are added to translate the AP 611ID into SAE core GW-Us when DC is provided. DNS controller 660 transfersthe translations for AP 611 to APP DNS 650. APP DNS 650 may now use thetranslations to serve UE 601 and other UEs over AP 611 with optimizedservices like LBO, NR, EN, and DC.

FIG. 7 illustrates UE 601 that receives the data communication servicesover co-located GW-Us. UE 601 is an example of UEs 101-103, although UEs101-103 may differ. UE 601 comprises Fifth Generation New Radio (5GNR)circuitry 711, CPU, memory, and user interfaces which are interconnectedover bus circuitry. 5GNR circuitry 711 comprises antennas, amplifiers,filters, modulation, analog-to-digital interfaces, DSP, and memory thatare coupled over bus circuitry. The antennas in UE 601 are coupled to AP611 over wireless 5GNR links. The user interfaces comprise graphicdisplays, machine controllers, sensors, cameras, transceivers, and/orsome other user components. The memories store operating systems, userapplications, and network applications. The network applicationscomprise Physical Layer (PHY), Media Access Control (MAC), Radio LinkControl (RLC), Packet Data Convergence Protocol (PDCP), Radio ResourceControl (RRC), and Service Data Adaptation Protocol (SDAP). The CPUexecutes the operating systems, user applications, and networkapplications to exchange network signaling and user data with AP 611over 5GNR circuitry 711 and the 5GNR links.

In UE 601, the CPU receives Uplink (UL) user data and signaling from theuser applications and transfers user data and signaling to memory. TheCPU executes the 5GNR network applications to process the UL user dataand signaling and Downlink (DL) 5GNR signaling to generate UL 5GNRsymbols that carry 5GNR data and RRC/N1 signaling. The 5GNR RRC/N1signaling may have network data like LBO, NR, EN, DC, and the like,although other codes might be used.

In 5GNR circuitry 711, the DSP processes the UL 5GNR symbols to generatecorresponding digital signals for the analog-to-digital interfaces. Theanalog-to-digital interfaces convert the digital UL signals into analogUL signals for modulation. Modulation up-converts the UL signals totheir carrier frequencies. The amplifiers boost the modulated UL signalsfor the filters which attenuate unwanted out-of-band energy. The filterstransfer the filtered UL signals through duplexers to the antennas. Theelectrical UL signals drive the antennas to emit corresponding wireless5GNR signals that transport the UL RRC/N1 signaling and 5GNR data to AP611.

In 5GNR circuitry 711, the antennas receive wireless signals from AP 611that transport Downlink (DL) RRC/N1 signaling and 5GNR data. The DLRRC/N1 signaling and 5GNR data may implement a network service like LBO,NR, EN, or DC. The antennas transfer corresponding electrical DL signalsthrough duplexers to the amplifiers. The amplifiers boost the receivedDL signals for filters which attenuate unwanted energy. In modulation,demodulators down-convert the DL signals from their carrier frequencies.The analog/digital interfaces convert the analog DL signals into digitalDL signals for the DSP. The DSP recovers DL 5GNR symbols from the DLdigital signals. The DSP transfer the DL 5GNR symbols to memory. TheCPUs execute the 5GNR network applications to process the DL 5GNRsymbols and recover the DL RRC/N1 signaling and 5GNR data. The CPUstransfer corresponding user data and signaling to the user applications.The user applications process the DL user data and signaling to interactwith the user interfaces. For example, a robot controller may drive amanufacturing robot.

In UE 601, the RRC network application exchanges user signaling with theuser applications. The SDAP network application exchanges user data withthe user applications. The RRC processes the UL user signaling and DLRRC/N1 signaling to generate DL user signaling and UL RRC/N1 signaling.The SDAP interworks between user data and 5GNR data and exchanges theuser data with the user applications. The RRC maps between RRC/N1signaling and Service Data Units (SDUs). The SDAP maps between the 5GNRdata and SDUs. The RRC and SDAP exchanges their SDUs with the PDCP. ThePDCP maps between the SDUs and PDUs. The PDCP exchanges the PDUs withthe RLC. The RLC maps between the PDUs and MAC logical channels. The RLCexchanges the RRC/N1 signaling and 5GNR data with the MAC over the MAClogical channels. The MAC maps between the MAC logical channels and MACtransport channels. The MAC exchanges the RRC/N1 signaling and 5GNR datawith the PHYs over the MAC transport channels. The PHYs maps between theMAC transport channels and PHY transport channels. The PHY exchanges the5GNR RRC/N1 signaling and 5GNR data with the PHYs in the AP 611 over thePHY transport channels in the 5GNR wireless links.

RRC functions comprise authentication, security, handover control,status reporting, Quality-of-Service (QoS), network broadcasts andpages, and network selection. SDAP functions comprise QoS marking andflow control. PDCP functions comprise security ciphering, headercompression and decompression, sequence numbering and re-sequencing,de-duplication. RLC functions comprise Automatic Repeat Request (ARQ),sequence numbering and resequencing, segmentation and resegmentation.MAC functions comprise buffer status, power control, channel quality,Hybrid Automatic Repeat Request (HARM), user identification, randomaccess, user scheduling, and QoS. PHY functions comprise packetformation/deformation, windowing/de-windowing,guard-insertion/guard-deletion, parsing/de-parsing, controlinsertion/removal, interleaving/de-interleaving, Forward ErrorCorrection (FEC) encoding/decoding, rate matching/de-matching,scrambling/descrambling, modulation mapping/de-mapping, channelestimation/equalization, Fast Fourier Transforms (FFTs)/Inverse FFTs(IFFTs), channel coding/decoding, layer mapping/de-mapping, precoding,Discrete Fourier Transforms (DFTs)/Inverse DFTs (IDFTs), and ResourceElement (RE) mapping/de-mapping.

FIG. 8 illustrates Access Point (AP) 611 that serves UE 601 with thedata communication services over co-located GW-Us. AP 611 is an exampleof APs 111-113, although APs 111-113 may differ. AP 611 comprisesDistributed Unit (DU) circuitry 811 and Centralized Unit (CU) circuitry812. DU circuitry 811 comprises 5GNR circuitry 821, CPUs, memory, andtransceivers (DU XCVR) that are coupled over bus circuitry. 5GNRcircuitry 821 comprises antennas, amplifiers, filters, modulation,analog-to-digital interfaces, DSP, and memory that are coupled over buscircuitry. CU circuitry 812 comprises CPU, memory, and transceivers thatare coupled over bus circuitry.

UE 601 is wirelessly coupled to the antennas in 5GNR circuitry 821 overthe wireless 5GNR links. The DU transceivers in DU circuitry 821 arecoupled to the CU transceivers in CU circuitry 812 over network datalinks. The network transceivers in CU circuitry 812 are coupled to NFVI670 over N2 links and N3 links.

In DU circuitry 811, the memories store operating systems and networkapplications. The network applications include at least some of: PHY,MAC, RLC, PDCP, RRC, and SDAP. In CU circuitry 812, the memories storeoperating systems, virtual components, and network applications. Thevirtual components comprise hypervisor modules, virtual switches,virtual machines, and/or the like. The network applications comprise atleast some of: PHY, MAC, RLC, PDCP, RRC, and SDAP.

The CPU in CU circuitry 712 executes some or all of the 5GNR networkapplications to drive the exchange of 5GNR data and signaling between UE601 and NFVI 670. The CPU in DU circuitry 811 executes some or all ofthe 5GNR network applications to drive the exchange of 5GNR data andsignaling between UE 601 and NFVI 670. The functionality split of the5GNR network applications between DU circuitry 811 and CU circuitry 812may vary.

In some examples, DU circuitry 811 and/or CU circuitry 812 host GW-Us,GW-Cs, APP DNS, OP DNS, DNS controllers, MME, AMF, or some other VNFs inthe same manner as NFVI 670. AGW-U and E-GWs that are hosted by DUcircuitry 811 and/or CU circuitry 812 qualify as co-located edge GW-Us.

In 5GNR circuitry 821, the antennas receive wireless signals from UE 601that transport UL 5GNR data and RRC/N1 signaling. The RRC/N1 signalingmay indicate network data like LBO, NR, EN, or DC. The antennas transfercorresponding electrical UL signals through duplexers to the amplifiers.The amplifiers boost the received UL signals for filters which attenuateunwanted energy. In modulation, demodulators down-convert the UL signalsfrom their carrier frequencies. The analog/digital interfaces convertthe analog UL signals into digital UL signals for the DSP. The DSPrecovers UL 5GNR symbols from the UL digital signals. In DU circuitry811 and/or CU circuitry 812, the CPUs execute the 5GNR networkapplications to process the UL 5GNR symbols to recover the UL RRC/N1signaling and 5GNR data. The network applications process the UL RRC/N1signaling, UL 5GNR data, DL N2/N1 signaling, and DL N3 data to generateDL RRC/N1 signaling, DL 5GNR data, UL N2/N1 signaling, and UL N3 data.In CU circuitry 412, the network transceivers transfer the UL N2/N1signaling and UL N3 data to NFVI 670 over the N2 and N3 links. The ULN2/N1 signaling may indicate network data for UE 601 like LBO, NR, EN,or DC. The UL N3 data may implement a service like LBO, NR, EN, or DC.

In CU circuitry 412, the network transceivers receive the DL N2/N1signaling and DL N3 data from NFVI 670 over the N2 and N3 links. The DLN2/N1 signaling and N3 data may implement a service like LBO, NR, EN, orDC. In DU circuitry 811 and/or CU circuitry 812, the CPUs execute the5GNR network applications to process the DL N2/N1 signaling and N3 datato generate the DL RRC/N1 signaling and the DL 5GNR data. The networkapplications process the DL RRC/N1 signaling and DL 5GNR data togenerate DL 5GNR symbols. In DU circuitry 811, the DSP processes the DL5GNR symbols to generate corresponding digital signals for theanalog-to-digital interfaces. The analog-to-digital interfaces convertthe digital DL signals into analog DL signals for modulation. Modulationup-converts the DL signals to their carrier frequencies. The amplifiersboost the modulated DL signals for the filters which attenuate unwantedout-of-band energy. The filters transfer the filtered DL signals throughduplexers to the antennas. The electrical DL signals drive the antennasto emit corresponding wireless 5GNR signals that transport the DL RRC/N1signaling and 5GNR data to UE 601 over the 5GNR links.

The RRC exchanges the N2/N1 signaling with MME 640 in NFVI 670. The SDAPexchanges N3 data with an SGW-U in NFVI 670. The RRC maps between theN2/N1 signaling and Service Data Units (SDUs). The SDAP maps between theN3 data and SDUs. The RRC and SDAP exchanges their SDUs with the PDCP.The PDCP maps between the SDUs and PDUs. The PDCP exchanges the PDUswith the RLC. The RLC maps between the PDUs and MAC logical channels.The RLC exchanges the RRC/N1 signaling and 5GNR data with the MAC overthe MAC logical channels. The MAC maps between the MAC logical channelsand MAC transport channels. The MAC exchanges RRC/N1 signaling and 5GNRdata with the PHYs over the MAC transport channels. The PHYs mapsbetween the MAC transport channels and PHY transport channels. The PHYexchanges the RRC/N1 signaling and 5GNR data with the PHYs in the UE 601over the PHY transport channels in the 5GNR wireless links.

RRC functions comprise authentication, security, handover control,status reporting, QoS, network broadcasts and pages, and networkselection. SDAP functions comprise QoS marking and flow control. PDCPfunctions comprise security ciphering, header compression anddecompression, sequence numbering and re-sequencing, de-duplication. RLCfunctions comprise ARQ, sequence numbering and resequencing,segmentation and resegmentation. MAC functions comprise buffer status,power control, channel quality, HARQ, user identification, randomaccess, user scheduling, and QoS. PHY functions comprise packetformation/deformation, windowing/de-windowing,guard-insertion/guard-deletion, parsing/de-parsing, controlinsertion/removal, interleaving/de-interleaving, FEC encoding/decoding,rate matching/de-matching, scrambling/descrambling, modulationmapping/de-mapping, channel estimation/equalization, FFTs/IFFTs, channelcoding/decoding, layer mapping/de-mapping, precoding, DFTs/IDFTs, and REmapping/de-mapping.

FIG. 9 illustrates the operation of UE 601, AP 611, and NFVIs 971-972 toserve UE 601 with special communication services over co-located GW-Us.NFVIs 971-972 are configured and operate like NFVI 670. The GW-Us inedge NFVI 971 are co-located edge GW-Us. The GW-Us in core NFVI 972 formintegrated SAE GW-Us for dedicated SAE core services. AMF 940 replacesMME 640.

The RRC in UE 601 and the RRC in AP 611 exchange 5GNR RRC/N1 signalingover their respective PDCPs, RLCs, MACs, and PHYs. The RRC in AP 611 andAMF 940 in core NFVI 672 exchange corresponding 5GNR N2/N1 signaling.AMF 940 interacts with UE 601 over N1 and with other VNFs like AUSF andUDM to perform UE authentication and security. AMF 940 interacts with UE601 over N1 and with other VNFs like PCF and SMF 941 to perform serviceselection. AMF 940 and SMF 941 select bearers and QoS for the selectedservice. In response to bearer and QoS selection, SMF 941 transfers N4signaling to SGW-C 641 that indicates the selected bearers, QoS, andother information for the selected service for UE 601.

In response to the N4 signaling, SGW-C 641 selects network data likeLBO, NR, EN, or DC based on the selected service. For example, SGW-C 641may select LBO for an internet-access service or select DC for an SAEcore service. SGW-C 641 generates a DNS message that requests atranslation of the AP 611 ID into an SGW-U ID using the included networkdata. SGW-C 641 transfers the DNS message to APP DNS 650. In response tothe DNS message, APP DNS 650 uses DDDS to translate the AP 611 ID intoan SGW-U ID using the included network data. If the network dataindicates LBO or NR low-latency, then APP DNS 650 translates the AP 611ID into an SGW-U ID for an SGW-U in edge NFVI 971. If the network dataindicates DC, then APP DNS 650 translates the AP 611 ID into an SGW-U IDfor an SGW-U in an SAE core in NFVI 972. APP DNS 650 transfers a DNSresponse indicating the selected SGW-U ID to SGW-C 641.

In response to the DNS response, SGW-C 641 signals the session formationto PGW-C 642. In response to the session information, PGW-C 642generates a DNS message that requests a translation of the SGW-U ID intoa PGW-U ID using the network data. PGW-C 642 transfers the DNS messageto APP DNS 650. In response to the DNS message, APP DNS 650 uses DDDS totranslate the SGW-U ID into a PGW-U ID using the network data. If thenetwork data indicates LBO or NR low-latency, then APP DNS 650translates the SGW-U ID into a PGW-U ID for a PGW-U in edge NFVI 971. Ifthe network data indicates DC, then APP DNS 650 translates the SGW-U IDinto a PGW-U ID for a PGW-U in the SAE core in NFVI 972.

APP DNS 650 transfers a DNS response indicating the selected PGW-U ID toPGW-C 641. In some examples, SGW-C 641 sends both DNS messages andshares the results with PGW-C 642. For example, SGW-C 641 may send bothDNS messages when DC is indicated and indicate the PGW-U ID to PGW-C642. SGW-C 641 transfers session control signaling for UE 601 to theselected SGW-U using the selected SGU-U ID. PGW-C 642 transfers sessioncontrol signaling for UE 601 to the selected PGW-U using the selectedPGU-U ID.

SGW-C 641 transfers N4 signaling to SMF 941 indicating the SGW-U ID andPGW ID, and SMF 941 signals the information to AMF 940. AMF 940transfers N2/N1 signaling to the RRC in AP 611 that indicates theselected bearers, SGW-U ID, and QoS. The RRC in AP 611 receives theresponse signaling and configures its network applications tocommunicate with UE 601 and the selected SGW-U. The RRC in AP 611transfers RRC/N1 signaling to the RRC in UE 601 over their respectivePDCPs, RLCs, MACs, and PHYs directing UE 601 to communicate with AP 611.In UE 601, the RRC configures its 5GNR network applications tocommunicate with AP 611. The RRC in AP 611 transfers N2/N1 signaling toAMF 960 indicating UE acceptance, and SMF 961 directs SGW-C 641 andPGW-C 642 to activate the bearers in the selected SGW-U and PGW-U thatserve UE 601.

The SDAP in UE 601 and the SDAP in AP 611 wirelessly exchange user dataover their respective PDCPs, RLCs, MACs, and PHYs to support the networkservice. AP 611 and the selected SGW-U exchange the user data to supportthe network service. The selected SGW-U and the selected PGW-U exchangethe user data to support the network service. In some cases, theselected PGW-U and the external systems exchange the user data tosupport the network service. In other cases, the selected PGW-U andanother PGW-U or SGW-U for another UE exchange the user data to supportthe network service. The co-located SGW-Us and PGW-Us in edge NFVI 971could be used to deliver excellent LBO and NR low-latency services to UE601. The co-located SGW-Us and PGW-Us in core NFVI 972 could be used todeliver excellent dedicated SAE core services to UE 601.

Before APP DNS 650 has the above translations for AP 611, UE 601 (oranother UE) wirelessly attaches to AP 611, and AP 611 transfers asession request to AMF 940. AMF 940 authenticates, authorizes, selects aservice for UE 601. SMF 941 transfers a create session request to SGW-C641. SGW-C 641 transfers a DNS message to APP DNS 650 that requeststranslation of the AP 611 ID into an SGW-U ID using network data. Sincethe translations for AP 611 are missing in this example, APP DNS 650transfers a DNS response that indicates a translation fault for AP 611to SGW-C 641.

SGW-C 641 receives the DNS response that indicates the translation faultfor AP 611. In response, SGW-C 641 transfers a translation fault noticethat indicates the TAI for UE 601, the AP ID for AP 611, and processinginstructions for network codes like LBO, NR, EN, and DC. DNS controller660 receives the translation fault notice and transfers a translationrequest to OP DNS 651 that has the TAI for UE 601. OP DNS 651 receivesthe translation request and translates the TAI into SGW-U IDs and PGW-UIDs that serve the TAI. OP DNS 651 transfers a translation response thatindicates the SGW-U IDs and the PGW-U IDs for the TAI.

DNS controller 660 receives the translation response and processes theSGW-U IDs and the PGW-U IDs against network topology data to determineco-located groups of the SGW-Us and PGW-Us. DNS controller 660 alsodetermines whether the co-location is at the network edge or in an SAEGW. To determine edge and core co-location, BGP listener 661 monitorsnetwork traffic to discover communication links between AP 611, theSGW-Us, and the PGW-Us. DNS controller 660 then enters a networktopology database to identify geographic information for AP 611 and thedetected SGW-Us and PGW-Us. The geographic information could begeographic coordinates, location IDs, NFVI IDs, and/or the like. DNScontroller 660 processes the geographic information for AP 611, theSGW-Us, and the PGW-Us to detect co-located SGW-Us and PGW-Us. DNScontroller 660 also processes the geographic information to detect AP611 proximity and SAE core proximity.

To indicate edge co-location where detected, DNS controller 660 adds ashared location ID like “EDGE611” to the co-located SGW-U IDs and PGW-UIDs in edge NFVI 971 that is near AP 611. DNS controller 660 adds“SAE972” to the co-located SGW-U IDs and PGW-U IDs in core NFVI 972. Perthe service instructions, DNS controller 660 also adds network data(like LBO, NR, EN, or DC) to the translations to branch the translationsfor AP 611 based on the network data. For example, LBO and NR nodestranslate the AP 611 ID into co-located edge GW-Us when LBO or NRnetwork data is provided. DC nodes translate the AP 611 ID into SAE coreGW-Us when DC network data is provided. DNS controller 660 transfers thetranslations for AP 611 to APP DNS 650. APP DNS 650 may now use thetranslations to serve UE 601 and other UEs over AP 611 with optimizedservices like LBO, NR, EN, and DC.

FIG. 10 illustrates Fifth Generation New Radio (5GNR) communicationnetwork 1000 to serve UE 1001 with data communication services overco-located 5G User Plane Functions (UPFs). 5GNR communication network1000 comprises an example of wireless communication network 100 althoughnetwork 100 may differ. 5GNR communication network 1000 comprises UE1001, 5GNR DU circuitry 1011, 5GNR CU circuitry 1012, and 5G Core (5GC)circuitry 1013. 5GC circuitry 1013 comprises a DNS controller, APP DNS,OP DNS, AMF, SMF, User Plane Function Control Plane (AUPF CP), AccessUPF User Plane (AUPF-U), and External UPF User Plane (EUPF-U). 5GNR CUcircuitry 1012 comprises an APP DNS, UPF CP, AUPF-U, and EUPF-U. 5GNR DUcircuitry 1011 comprises an AUPF-U and EUPF-U. The AUPF-U and EUPF-U inDU circuitry 1011 are co-located edge GW-Us. The AUPF-U and EUPF-U in CUcircuitry 1012 are also co-located edge GW-Us. The AUPF-U and EUPF-U in5GC circuitry 1013 form an integrated SAE GW-U in a dedicated SAE core.

UE 1001 and 5GNR DU circuitry 1011 exchange 5GNR RRC/N1 signaling overwireless 5GNR links. 5GNR DU circuitry 1011 and 5GNR CU circuitry 1012exchange 5GNR signaling over fronthaul links. 5GNR CU circuitry 1012 andthe AMF in 5GC circuitry 1013 exchange 5GNR N1/N2 signaling overbackhaul links. The AMF interacts with UE 1001 over the N1 signalingauthenticate and authorize UE 1001. The AMF and SMF interact with UE1001 over N1 and with other VNFs to select a service. The AMF and SMFselect bearers and QoS for the selected service. In response to an edgeservice selection, the SMF transfers N4 signaling to the UPF CP in 5GNRCU circuitry 1012 that indicates the selected bearers, QoS, and otherinformation for the selected service for UE 601.

In response to the N4 signaling, the UPF CP in CU circuitry 1012 selectsnetwork data like LBO, NR, EN, or DC based on the selected edge service.The UPF CP in CU circuitry 1012 generates a DNS message that requests atranslation of the ID for 5GNR DU 1011 and/or CU circuitry 1012 into anAUPF-U ID using the included network data. The UPF CP in CU circuitry1012 transfers the DNS message to the APP DNS in CU circuitry 1012. Inresponse to the DNS message, the APP DNS uses DDDS to translate the IDfor DU circuitry 1011 and/or CU circuitry 1012 into an AUPF-U ID usingthe included network data. For edge 5GNR low-latency between 5GNR UEs,the APP DNS in CU circuitry 1012 translates the DU/CU ID into an AUPF-UID for an AUPF-U in DU circuitry 1011. For edge LBO, DC, or EN the APPDNS in CU circuitry 1012 translates the DU/CU ID into an AUPF-U ID foran AUPF-U in CU circuitry 1012.

In response to the DNS response, the UPF CP in CU circuitry 1012generates another DNS message that requests a translation of the AUPF-UID into a EUPF-U ID using the network data. The UPF CP transfers the DNSmessage to APP DNS 650 in CU circuitry 1012. In response to the DNSmessage, the APP DNS uses DDDS to translate the AUPF-U ID into an EUPF-UID using the network data. For an edge low-latency NR between UEs, theAPP DNS translates the AUPF-U ID into an EUPF-U ID for an EUPF-U in DUcircuitry 1011. For edge LBO, DC, or EN the APP DNS in CU circuitry 1012translates the DU/CU ID into an AUPF-U ID for an AUPF-U in CU circuitry1012.

The APP DNS in CU circuitry 1012 transfers a DNS response indicating theselected EUPF-U ID to the UPF CP in CU circuitry 1012. The UPF CP in CUcircuitry 1012 transfers N4 signaling to the SMF indicating the AUPF-UID and the EUPF-U ID, and the SMF signals the information to the AMF.The AMF transfers N2/N1 signaling to CU circuitry 1011 that indicatesthe selected bearers, AUPF-U ID, EUPF-U ID, and QoS. 5GNR DU circuitry1011 and/or CU circuitry 1012 receive the N2/N1 signaling and configurethe network applications to communicate with UE 1001 and the selectedAUPF-U. 5GNR DU circuitry 1011 and/or CU circuitry 1012 signal UE 1001to communicate with DU circuitry 1012. UE 1001 configures its 5GNRnetwork applications to communicate with DU circuitry 1011. 5GNR DUcircuitry 1011 and/or CU circuitry 1012 transfer N2/N1 signaling to theAMF indicating UE acceptance, and the SMF directs the UPF CP in CUcircuitry 1012 to activate the bearers that serve UE 1001. The UPF CP inCU circuitry 1012 directs the selected AUPF-U and EUPF-U to serve UE1001 with the QoS over the bearers.

UE 601 and the DU circuitry 1011 wirelessly exchange user data tosupport the network service. DU circuitry 1011 and the AUPF in DUcircuitry 1011 or CU circuitry 1012 exchange the user data to supportthe network service. The AUPF in DU circuitry 1011 or CU circuitry 1012and the AUPF in DU circuitry 1011 or CU circuitry 1013 exchange the userdata to support the network service. The EUPF in DU circuitry 1011 or CUcircuitry 1012 and external systems, AUPFs, or EUPFs exchange the userdata to support the network service. The co-located AUPF-Us and EUPF-Usin DU circuitry 1011 and CU circuitry 1012 deliver excellent LBO and NRlow-latency services to UE 1001.

In response to an SAE core service selection, the SMF transfers N4signaling to the UPF CP in 5GC circuitry 1013 that indicates theselected bearers, QoS, and other information for the selected servicefor UE 601. The UPF CP in 5GC circuitry 1013 selects network data likeNR, EN, or DC based on the selected core service. The UPF CP in 5GCcircuitry 1013 generates a DNS message that requests a translation ofthe ID for 5GNR DU circuitry 1011 and/or CU circuitry 1012 into anAUPF-U ID using the included network data. The UPF CP transfers the DNSmessage to the APP DNS 5GC circuitry 1013. The APP DNS uses DDDS totranslate the ID for DU circuitry 1011 and/or CU circuitry 1012 into anAUPF-U ID using the included network data. For core NR, EN, or DC, theAPP DNS in 5GC circuitry 1013 translates the DU/CU ID into an AUPF-U IDfor an AUPF-U in 5GC core circuitry 1013. The APP DNS uses DDDS totranslate the AUPF-U ID into an EUPF-U ID in 5GC core circuitry 1013using the network data. For core NR, EN, or DC, the APP DNS translatesthe AUPF-U ID into an EUPF-U ID for an EUPF-U in 5GC circuitry 1013. TheAUPF-U and EPF-U in 5GC circuitry 1013 exchange the user data to supportthe selected core service.

Before the APP DNS in CU circuitry 1012 or 5GC circuitry 1013 has theabove translations for DU circuitry 1011 and/or CU circuitry 1012, UE1001 (or another UE) wirelessly attaches to DU circuitry 1011, and CUcircuitry 1012 transfers a session request to the AMF. The AMFauthenticates, authorizes, selects a service for UE 1001. The SMFtransfers a create session request to a UPF CP. The UPF CP transfers aDNS message that requests translation of the DU/CU ID into an AUPF-Uusing the network data. Since the translations is missing in thisexample, the APP DNS transfers a DNS response that indicates atranslation fault for the DU/CU ID.

The UPF CP receives the DNS response that indicates the translationfault. In response, UPF CP transfers a translation fault notice thatindicates the TAI for UE 1001, the DU/CU ID, and processing instructionsfor network codes like LBO, NR, EN, and DC. The DNS controller receivesthe translation fault notice and transfers a translation request to theOP DNS that has the TAI for UE 1001. The OP DNS receives the translationrequest and translates the TAI into AUPF-U IDs and EUPF-U IDs. The OPDNS transfers a translation response that indicates the AUPF-U IDs andEUPF-U IDs for the TAI of UE 1001.

The DNS controller receives the translation response and processes theAUPF-U IDs and the EUPF-U IDs against network topology data to determineco-located groups of the AUPF-Us and EUPF-Us. The DNS controller alsodetermines whether the co-location is at the network edge or in an SAEGW. To determine co-location at the edge or in an SAE core, the DNScontroller uses a BGP listener to monitor network traffic and discovercommunication links between the SDAP in DU circuitry 1011 or CUcircuitry 1012 and the AUPF-Us, and between the AUPF-Us and the EUPF-Us.The DNS controller enters a topology database to identify geographicdata for DU circuitry 1011, CU circuitry 1012, 5GC circuitry 1013, andthe detected AUPF-Us and EUPF-Us. The geographic information could begeographic coordinates, location IDs, NFVI IDs, and/or the like. The DNScontroller processes the geographic information for DU circuitry 1011,CU circuitry 1012, 5GC circuitry 1013, and the detected AUPF-Us andEUPF-Us to detect co-located AUPF-Us and EUPF-Us. The DNS controlleralso processes the geographic information to detect edge proximity to DUcircuitry 1011 and/or CU circuitry 1012.

To indicate edge co-location where detected, the DNS controller adds ashared location ID like “DU1011” or “CU1012” to the co-located AUPF-UIDs and EUPF-U IDs in DU circuitry 1011 or CU circuitry 1012. Per theservice instructions, the DNS controller also adds network data (likeLBO, NR, EN, or DC) to branch the translations for the DU/CU ID based onthe network data. For example, LBO and NR nodes are added to translatethe DU/CU ID into co-located edge UPF-Us when LBO or NR low-latency isindicated. DC nodes are added to translate the DU/CU ID into SAE UPF-UIDs when DC is indicated. The DNS controller transfers the translationsfor the DU/CU ID to the APP DNS in CU circuitry 1012 and in 5GCcircuitry 1013. Both APP DNS may now use the translations to serve UE1001 and other UEs over DU circuitry 1011, CU circuitry 1012, and 5GCcircuitry 1013 with optimized services like LBO, NR, EN, and DC.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose wireless networkcircuitry to wirelessly serve UEs with wireless communication servicesover co-located edge gateways. The computer hardware comprisesprocessing circuitry like CPUs, DSPs, GPUs, transceivers, bus circuitry,and memory. To form these computer hardware structures, semiconductorslike silicon or germanium are positively and negatively doped to formtransistors. The doping comprises ions like boron or phosphorus that areembedded within the semiconductor material. The transistors and otherelectronic structures like capacitors and resistors are arranged andmetallically connected within the semiconductor to form devices likelogic circuitry and storage registers. The logic circuitry and storageregisters are arranged to form larger structures like control units,logic units, and Random-Access Memory (RAM). In turn, the control units,logic units, and RAM are metallically connected to form CPUs, DSPs,GPUs, transceivers, bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose wireless networkcircuitry to wirelessly serve UEs with wireless communication servicesover co-located edge gateways.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless communicationnetwork to use co-located User Plane Functions (UPFs), the methodcomprising: a control-plane function receiving a session request for aUser Equipment (UE) over a wireless access point that has a wirelessaccess node Identifier (ID) and responsively transferring a co-locatedUPF request for the wireless access point ID to a naming system; thenaming system receiving the co-located UPF request, and in response,detecting a co-location translation fault for the wireless access pointID and transferring the wireless access point ID to a translationcontroller; the translation controller receiving the wireless accesspoint ID, and in response, determining a set of the co-located UPFs forthe wireless access node and transferring co-location translationinformation for the wireless access point ID and a set of co-located UPFIDs for the set of co-located UPFs to the naming system; thecontrol-plane function receiving another session request for another UEover the wireless access point and responsively transferring anotherco-located UPF request for the wireless access point ID to the namingsystem; the naming system receiving the other co-located UPF request andtranslating the wireless access point ID into the set of co-located UPFIDs and transferring the set of the co-located UPF IDs to thecontrol-plane function; and the control-plane function receiving the setof the co-located UPF IDs and signaling the set of the co-located UPFsto serve the UE over the wireless access point.
 2. The method of claim 1wherein the translation controller transferring the co-locationtranslation information to the naming system comprises generating thetranslation information having location IDs in the co-located UPF IDs.3. The method of claim 1 wherein the translation controller transferringthe co-location translation information to the naming system comprisesgenerating the translation information having a common location ID inthe co-located UPF IDs.
 4. The method of claim 1 wherein the translationcontroller transferring the co-location translation information to thenaming system comprises generating the translation information having anedge location ID in the co-located UPF IDs.
 5. The method of claim 1wherein the control-plane function signaling the set of the co-locatedUPFs to serve the UE over the wireless access point comprises signalingthe set of the co-located UPFs to serve a Fifth Generation New Radio(5GNR) low-latency service to the UE.
 6. The method of claim 1 whereinthe control-plane function signaling the set of the co-located UPFs toserve the UE over the wireless access point comprises signaling the setof the co-located UPFs to serve a Local Breakout (LBO) service to theUE.
 7. The method of claim 1 wherein the naming system comprises aDomain Name System (DNS).
 8. The method of claim 1 wherein thecontrol-plane function comprises an Access and Mobility ManagementFunction (AMF).
 9. The method of claim 1 wherein the control-planefunction comprises a Mobility Management Entity (MME).
 10. The method ofclaim 1 wherein: the control-plane function comprises a SystemArchitecture Evolution Gateway (SAE GW) control-plane; and the set ofthe co-located UPFs comprise a System Architecture Evolution Gateway(SAE GW) user-plane.
 11. A wireless communication network to useco-located User Plane Functions (UPFs), the wireless communicationnetwork comprising: a control-plane function configured to receive asession request for a User Equipment (UE) over a wireless access pointthat has a wireless access node Identifier (ID) and responsivelytransfer a co-located UPF request for the wireless access point ID to anaming system; the naming system configured to receive the co-locatedUPF request, and in response, detect a co-location translation fault forthe wireless access point ID and transfer the wireless access point IDto a translation controller; the translation controller configured toreceive the wireless access point ID, and in response, determine a setof the co-located UPFs for the wireless access node and transferco-location translation information for the wireless access point ID anda set of co-located UPF IDs for the set of co-located UPFs to the namingsystem; the control-plane function configured to receive another sessionrequest for another UE over the wireless access point and responsivelytransfer another co-located UPF request for the wireless access point IDto the naming system; the naming system configured to receive the otherco-located UPF request and translate the wireless access point ID intothe set of co-located UPF IDs and transfer the set of the co-located UPFIDs to the control-plane function; and the control-plane functionconfigured to receive the set of the co-located UPF IDs and signal theset of the co-located UPFs to serve the UE over the wireless accesspoint.
 12. The wireless communication network of claim 11 wherein thetranslation controller is configured to generate the translationinformation having location IDs in the co-located UPF IDs.
 13. Thewireless communication network of claim 11 wherein the translationcontroller is configured to generate the translation information havinga common location ID in the co-located UPF IDs.
 14. The wirelesscommunication network of claim 11 wherein the translation controller isconfigured to generate the translation information having an edgelocation ID in the co-located UPF IDs.
 15. The wireless communicationnetwork of claim 11 wherein the control-plane function is configured tosignal the set of the co-located UPFs to serve a Fifth Generation NewRadio (5GNR) low-latency service to the UE.
 16. The wirelesscommunication network of claim 11 wherein the control-plane function isconfigured to signal the set of the co-located UPFs to serve a LocalBreakout (LBO) service to the UE.
 17. The wireless communication networkof claim 11 wherein the naming system comprises a Domain Name System(DNS).
 18. The wireless communication network of claim 11 wherein thecontrol-plane function comprises an Access and Mobility ManagementFunction (AMF).
 19. The wireless communication network of claim 11wherein the control-plane function comprises a Mobility ManagementEntity (MME).
 20. The wireless communication network of claim 11wherein: the control-plane function comprises a System ArchitectureEvolution Gateway (SAE GW) control-plane; and the set of the co-locatedUPFs comprise a System Architecture Evolution Gateway (SAE GW)user-plane.